Method and apparatus to postpone UE from handover to an overloaded radio network from another radio network

ABSTRACT

A node of a secondary RAT that is in communication with a primary node of a primary RAT and UEs that are able to communicate by way of the primary and secondary RATs. The node includes a network interface unit of the node which receives a message from the primary node that indicates that the primary RAT is in an overload condition. The node includes a processing unit of the node which forms UE messages for the UEs not to try to communicate with the primary RAT, the network interface unit of the node sending the messages to the UEs. A method of a node of a secondary RAT that is in communication with a primary node of a primary RAT and UEs that are able to communicate by way of the primary and secondary RATs.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 13/721,322, filed Dec. 20, 2012, which claims the benefit of U.S. Provisional Patent Application No. 61/679,893 filed Aug. 6, 2012, the contents of which are incorporated herein by reference.

TECHNICAL FIELD

The present invention is related to postponing a UE from handover to an overloaded radio network from another radio network. (As used herein, references to the “present invention” or “invention” relate to exemplary embodiments and not necessarily to every embodiment encompassed by the appended claims.) More specifically the present invention pertains to postponing a UE from handover to an overloaded radio network from another radio network by a node of the overloaded radio network sending a message regarding its overload condition to a node in the other radio network.

BACKGROUND

This section is intended to introduce the reader to various aspects of the art that may be related to various aspects of the present invention. The following discussion is intended to provide information to facilitate a better understanding of the present invention. Accordingly, it should be understood that statements in the following discussion are to be read in this light, and not as admissions of prior art.

Due to the introduction of advanced wireless Radio Access Technologies (RAT), many mobile network operators are forced to deploy systems based on new technology to meet the consumer demands but still need to keep the legacy system for different reasons. Since different RATs may be based on different radio technology, the two RATs deployed by the operator may not be backward compatible. For this reason, inter-RATs mechanisms were developed to allow network to control multi-RATs supported UE switching between different RATs within operator's networks. The inter-RATs mechanism also provide requirements to guide UE to determine which RAT it should be camp on if multiple RATs are detected in the network.

Operators with multiple RATs supported in the network usually configure one of the RAT as the primary RAT. While UEs are in idle, the UEs are usually configured by the operator to search for primary RAT and camp on the primary RAT when possible.

UEs sometime may not camp on the primary RAT due to different reasons. For example, the UE was located in an area only secondary RAT service is provided, and just move into an area with services from both RATs are provided. Another possibility could be that the UE went to secondary RAT to access the network (i.e. with a dedicated channel) because it could not get reasonable channel strength form primary RAT when user is trying to access the network. Regardless how the UE end up camp on the secondary RAT, there are inter-RAT InterWorking (IWK) mechanisms exist to move the UE back to primary RAT when UE is in idle or even when UE has a dedicate channel assigned. Using LTE and eHRPD IWK as an example, two eHRPD (as secondary RAT) mechanisms exists that allows idle UE re-select the LTE (as primary RAT) as the RAT to camp on. The two mechanisms are either based on MMSS (Multi-Mode System Selection), which has minimum control from network, or Other RAT Neighbor List method, which allows network have better control on UE's RAT selection behavior. For UE accessing the eHRPD dedicated channel, the eAN can also use redirection mechanism to handover the UE to LTE system.

The existing inter-RAT mechanisms work well in normal condition with the assumption that the primary RAT (e.g. LTE) has greater capacity (e.g. allows more UEs attach to the network) compare to the secondary RAT (e.g. legacy system such as HRPD). When overload on primary RAT occurs, the existing inter-RAT mechanisms can also redirect the UE to the secondary RAT to address the overload situation on the primary RAT.

Since inter-RAT functions works both ways. When the UEs are redirected to the secondary RAT due to overload situation on primary RAT, the inter-RAT IWK function on secondary RAT also kick in and attempt to redirect the UE back to the primary RAT since the system is configured primary RAT as the default camp on system for these UE. Since secondary RAT has no knowledge of primary RAT's load condition, UEs may ping-ponging between two RATs and drastically reduce the network efficiency.

BRIEF SUMMARY OF THE INVENTION

The present invention pertains to a node of a secondary RAT that is in communication with a primary node of a primary RAT and UEs that are able to communicate by way of the primary and secondary RATs. The node comprises a network interface unit of the node which receives a message from the primary node that indicates that the primary RAT is in an overload condition. The node comprises a processing unit of the node which forms UE messages for the UEs not to try to communicate with the primary RAT, the network interface unit of the node sending the messages to the UEs.

The present invention pertains to a method of a node of a secondary RAT that is in communication with a primary node of a primary RAT and UEs that are able to communicate by way of the primary and secondary RATs. The method comprises the steps of receiving at a network interface unit of the node a message from the primary node that indicates that the primary RAT is in an overload condition. There is the step of forming with a processing unit of the node UE messages for the UEs not to try to communicate with the primary RAT. There is the step of sending the messages through the network interface unit of the node to the UEs.

BRIEF DESCRIPTION OF THE DRAWING

In the accompanying drawings, the preferred embodiment of the invention and preferred methods of practicing the invention are illustrated in which:

FIG. 1 shows an example based on example embodiment 1.

FIG. 2 shows an example based on example embodiment 2.

FIG. 3 is a schematic representation of the present invention.

FIG. 4 is a block diagram of a node of the present invention.

DETAILED DESCRIPTION

Referring now to the drawings wherein like reference numerals refer to similar or identical parts throughout the several views, and more specifically to FIGS. 3 and 4 thereof, there is shown a node 10 of a secondary RAT 22 that is in communication with a primary node 16 of a primary RAT 20 and UEs that are able to communicate by way of the primary and secondary RATs 22. The node 10 comprises a network interface unit 12 of the node 10 which receives a message from the primary node 16 that indicates that the primary RAT 20 is in an overload condition. The node 10 comprises a processing unit 14 of the node 10 which forms UE messages for the UEs not to try to communicate with the primary RAT 20, the network interface unit 12 of the node 10 sending the messages to the UEs.

A broadcast message may be sent from the network interface unit 12 to the UEs with an indication that the primary RAT 20 is in the overload condition and each UE is not to switch back to the primary RAT 20. The network interface unit 12 may receive from a UE of the UEs an uplink message that the primary RAT 20 is in an overload condition. The broadcast message may affect an Other RAT Neighbor List Function in each UE so that each UE does not switch back to the primary RAT 20. The network interface unit 12 may stop sending the indication that the primary RAT is in the overload condition in the broadcast message from the network interface unit 12 of the node 10 after the network interface unit 12 has not received the uplink message for a predetermined time from any of the UEs that the primary RAT 20 is overloaded.

The network interface unit 12 may receive from a dual interface 24 in communication with the primary and the secondary RATs 22 that the primary RAT 20 is in the overload condition. The network interface unit 12 of the node 10 may receive an overload-off indication from the dual interface 24 when the overload condition of the primary RAT 20 has ended, and the processing unit 14 of the node 10 stops sending broadcast messages to the UEs that the primary RAT 20 is in the overload condition.

The present invention pertains to a method of a node 10 of a secondary RAT 22 that is in communication with a primary node 16 of a primary RAT 20 and UEs that are able to communicate by way of the primary and secondary RATs 20, 22. The method comprises the steps of receiving at a network interface unit 12 of the node 10 a message from the primary node 16 that indicates that the primary RAT 20 is in an overload condition. There is the step of forming with a processing unit 14 of the node 10 UE messages for the UEs not to try to communicate with the primary RAT 20. There is the step of sending the messages through the network interface unit 12 of the node 10 to the UEs.

The sending step may include the step of sending a broadcast message to the UEs with an indication that the primary RAT 20 is in the overload condition and each UE is not to switch back to the primary RAT 20. The receiving step may include the step of receiving from a UE of the UEs an uplink message that the primary RAT 20 is in an overload condition. The sending step may include the step of the broadcast message affecting an Other RAT Neighbor List Function in each UE so that each UE does not switch back to the primary RAT 20. There may be the step of stopping sending the indication that the primary RAT is in the overload condition in the broadcast message from the network interface unit 12 of the node 10 after the network interface unit 12 has not received the uplink message for a predetermined time from any of the UEs that the primary RAT 20 is overloaded.

The receiving step may include the step of receiving from a dual interface 24 in communication with the primary and the secondary RATs 20, 22 that the primary RAT 20 is in the overload condition. There may be the steps of the network interface unit 12 of the node 10 receiving an overload-off indication from the dual interface 24 when the overload condition of the primary RAT 20 has ended, and the processing unit 14 of the node 10 stopping sending broadcast messages to the UEs that the primary RAT 20 is in the overload condition.

In the operation of the invention, when a Primary RAT 20 is in overload condition and forced to redirect an UE to a secondary RAT 22, the Secondary RAT 22 needs to be informed about the overload situation of the Primary RAT 20. With this information, the Secondary RAT 22 can take appropriate action to reduce or avoid ping-pong effect due to making UEs return to the overloaded Primary RAT 20.

There are two possible ways to convey overload information from one RAT (e.g. Primary overloaded RAT) to another RAT (e.g. Secondary RAT 22):

UE Assisted RAT System Overload Indication:

-   -   1. If the primary RAT 20 system is overloaded, and determined to         redirect an UE to different RAT (secondary) system, the primary         RAT's 20 downlink message that instruct the UE to redirect to         secondary RAT 22 system contain primary RAT's 20 network         overload indication. This network overload information can be an         explicit “network overload” indication in the downlink message         or can be implicit information. Using LTE as an example, after         several failed attempt to redirect UE to different LTE         frequencies, the corresponding downlink message (e.g., either         release message or reject message or other appropriate downlink         message) marked the priority of the Secondary RAT 22 as the         highest priority (existing function). Making Secondary RAT 22         with highest priority compare to Primary RAT 20 (e.g. LTE) can         be viewed by UE as a network overload.     -   2. UE reselect/redirect to Secondary RAT 22 due to the         appropriate downlink message from Primary RAT 20 that cause the         RAT reselect/redirect.     -   3. After successfully acquire Secondary RAT 22 system, the UE         sends a Secondary RAT's 22 uplink message containing information         indicates that the Primary RAT 20 is overloaded. The UE set the         uplink message's Primary RAT 20 overload indication based on the         explicit or implicit overload information obtained before         switching to Secondary RAT 22. UE only include the Primary RAT         20 overloaded indication in the very first uplink message that         is used to carry this kind of indication (message to be sent to         secondary RAT 22) after switching over from primary RAT 20.         While in the secondary RAT 22, if the same message is to be sent         again for any reason, the UE does not include Primary RAT 20         overloaded indication any more in the subsequence occurrence of         this uplink message.     -   4. When the RAN (of Secondary RAT 22 system) receives UE uplink         message indicates that Primary RAT 20 system is overloaded, the         RAN takes action to inform UEs not to switch (e.g. handover) to         Primary RAT 20 system. There are different ways of doing this         function listed as follows:         -   RAN can use broadcast message to broadcast Primary RAT 20             system overload. As long as this overload indication is set             in the broadcast message, the UE does not attempt to switch             back to Primary RAT 20 (e.g. using MMSS or any “Other             Inter-RAT mechanisms”).         -   Beside broadcast Primary RAT 20 system overload information             in the broadcast message, if Other RAT Neighbor List             function is implemented, the RAN can also stop this function             or modify the function appropriately (e.g. change the             priority of channels, etc.) during the Primary RAT 20             overload period.     -   5. RAN of the Secondary RAT 22 system continues to broadcast         Primary RAT 20 system overload information as long as it         continues to receive uplink message from any UE that have the         Primary RAT 20 system overload indicator set.     -   6. UEs supports both RAT systems do not attempt to switch back         (e.g. handover or redirect) to primary RAT 20 system (e.g. even         though the switching requirements are met based on implemented         RAT system selection function(s)) as long as secondary RAT 22         broadcast “Primary RAT overloaded” indication.     -   7. RAN of the Secondary RAT 22 system may stop broadcast the         Primary RAT 20 system overload information if the RAN has not         receive any UE indicating Primary RAN system overload in x         minutes since last UE contains the overload information.     -   8. inter-RAT mechanisms resume normal function on both UE and         RAN sides after RAN of the Secondary RAT 22 system stop         broadcast Primary RAT 20 system overload information.

Network Based RAT System Overload Indication:

-   -   1. The Radio Resource Management (RRM) function of the primary         RAT 20 system (or any network entity manage the network overload         condition) inform the RRM function of the secondary RAT 22         system that the primary RAT 20 system is overloaded. This         information can be passed from primary RAT 20 system to         secondary RAT 22 system through interface connected to both         systems.     -   2. After the secondary RAT 22 system receives the overload         indication from primary RAT 20 system, the secondary system RAN         perform step 4 of “UE assisted” method above. The only         difference is that instead of getting the overload indication         from UE, the overload indication is coming from the primary RAT         20 system through interface connecting to both systems.     -   3. RAN of the secondary RAT 22 system continues to broadcast         Primary RAT 20 system overload indication as long as it         continues to receive overload indication from primary RAT 20         system or the secondary RAT 22 system does not receive         “overload-off” indication from primary RAT 20 system (i.e. the         primary RAT 20 system may only sends overload indication once         instead of continuously pass this information to secondary RAT         22 system).     -   4. UEs supports both RAT systems do not attempt to switch back         (e.g. handover or redirect) to primary RAT 20 system (e.g. even         though the switching requirements are met based on implemented         RAT system selection function(s)) as long as secondary RAT 22         broadcast “Primary RAT overloaded” indication.     -   5. When primary RAT 20 system overload condition diminished, the         primary RAT 20 system sends “overload-off” indication to         secondary RAT 22 system. Upon receiving this “overload-off”         indication, the RAN of the secondary RAT 22 system may stop         broadcast the primary RAT 20 system overload indication.     -   6. inter-RAT mechanisms resume normal function on both UE and         RAN sides after RAN of the Secondary RAT 22 system stop         broadcast Primary RAT 20 system overload information.

Even though the methods mentioned above using “primary” and “secondary” to identify the different RAT systems, but the system can also be viewed as “source” and “target” systems where the “secondary” system is identified as the “target” system.

Even though the methods mentioned above using “primary” and “secondary” to identify the different RAT systems, but the system can also be viewed as “source” and “target” systems where the “secondary” system is identified as the “target” system. If “source” and “target” is used, the invention can be viewed as how to prevent UE switching back to overloaded “source” system.

The concept of the invention provided above can be applicable from any RAT system to another RAT system. For description purpose, EUTRAN and eHRPD IWK are used for example purpose where EUTRAN is identified as the primary RAT 20 system and eHRPD is identified as secondary RAT 22 system:

EUTRAN Overloaded; UE Assisted Method:

-   -   When EUTRAN is overloaded, it may start reject or release (e.g.         RRCConnectionReject or RRCConnectionRelease) UEs from EUTRAN         frequencies and de-prioritize some of the EUTRAN frequencies.         When all available EUTRAN frequencies are overloaded, the EUTRAN         start reject or release some of the UEs and, in the message,         inform UE to redirect/reselect eHRPD system.         -   eNB may include “EUTRAN overloaded” indicator when the             message is used to re-direct the UE to eHRPD (preferred); or         -   the release/reject message make cdma frequency as the             highest priority. Under this situation, UE set “EUTRAN             overload” indicator.     -   When UE moved to eHRPD, the UE sends an HRPD signalling message         (e.g. ConnectionRequest message or RouteUpdate message) to         include “EUTRAN overloaded” indication. The UE only include the         “EUTRAN overloaded” indication once right after switching to         eHRPD from EUTRAN. For example, if ConnectionRequest message is         used to carry the EUTRAN overloaded” indication, the UE only         include this indication in the first ConnectionRequest message         UE send after it switches from EUTRAN to eHRPD. UE does not         include this indication in any subsequent ConnectionRequest         message as long as it is staying in the eHRPD system.     -   eHRPDeAN receive the uplink message with “EUTRAN overloaded”         indication set. Then, eAN marked broadcast message (e.g.         QuickConfigmessage) with “EUTRAN overloaded” indication set. If         eAN also broadcast OtherRATNeighbour List message, the eAN can         either stop broadcast the message or adjust the content of the         message such that the UE will not use the information included         in the message to perform idle handover back to EUTRAN. The eAN         also initiate and starts the overload timer. The overload timer         is defined as a period of x minutes (the length of x is defined         by operator). The timer is reset is eAN receive at least one UE         with “EUTRAN overloaded” indication before timer expires.     -   When UEs receive eAN broadcast message indicating “EUTRAN         overloaded”, the UEs temporally disable using PRL/MMSS function         (or any other system reselection function) to switch back to         EUTRAN. If the OtherRATNeighbour List message is broadcasted by         eAN, the UE follow the guideline provided in the message to         determine whether it should switch back to EUTRAN.     -   UE switch from LTE to eHRPD will not set “EUTRAN overloaded”         indication in uplink message (e.g. ConnectionRequest message) if         the switching is not triggered due to LTE overload situation.     -   eAN continues to mark “EUTRAN overloaded” in the broadcast         message if overload timer is not expired. When overload timer         expired, the eAN stop broadcasting “EUTRAN overloaded”         indication in the overhead message. If OtherRAT Neighbor list         message is supported, the message is transmitted with normal         parameters.     -   UEs detect that eAN remove the “EUTRAN overloaded” indication,         the UEs can start using normal operation and perform EUTRAN         reselection when appropriate.

EUTRAN Overloaded; Network Based Indication Method:

-   -   When EUTRAN is overloaded, it may start reject or release (e.g.         RRCConnectionReject or RRCConnectionRelease) UEs from EUTRAN         frequencies and de-prioritize some of the EUTRAN frequencies.         When all available EUTRAN frequencies are overloaded, the EUTRAN         start reject or release some of the UEs. For the co-located         networks (LTE/CDMA) or connected inter-RAT networks, a “EUTRAN         overloaded” indication is passed from LTE RRM component to cdma         RRM component. The interface used can be a proprietary         interface, or a standards defined interface.     -   Upon receiving the “EUTRAN overloaded” indication from LTE         network, the eHRPDeAN marked broadcast message (e.g. QuickConfig         message) with “EUTRAN overloaded” indication. If eAN also         broadcast OtherRATNeighbour List message, the eAN can either         stop broadcast the message or adjust the content of the message         such that the UE will not use the information included in the         message to perform idle handover back to EUTRAN.     -   When UEs receive eAN broadcast message indicating “EUTRAN         overloaded”, the UEs temporally disable using PRL/MMSS function         (or any other system reselection function) to switch back to         EUTRAN. If the OtherRATNeighbour List message is broadcasted by         eAN, the UE follow the guideline provided in the message to         determine whether it should switch back to EUTRAN.     -   When LTE network overload condition diminished, the LTE network         pass the “LTE not overload” indication to HRPD network. Upon         receiving this indication, the eAN stop broadcasting “EUTRAN         overloaded” indication in the overhead message. If OtherRAT         Neighbor list message is supported, the message is transmitted         with normal parameters.     -   UE detects that eAN remove the “EUTRAN overloaded” indication,         the UE can start using normal operation and perform EUTRAN         reselection when appropriate.

Example Embodiment 1

-   -   1. The LTE RRM sends “EUTRAN overloaded” indication to eHRPD         RRM.     -   2. eHRPDeAN broadcast “EUTRAN overloaded” indication in the         overhead message (e.g. QuickConfig). If OtherRATNeighborList         message is also supported, eAN take action to stop sending the         message (or other treatment to the message).     -   3. UE detect the “EUTRAN overloaded” indication from eAN, UE         remain in eHRPD system and does not perform LTE re-selection         mechanism (e.g. LTE re-selection based on MMSS or other         methods).     -   4. LTE RRM sends “EUTRAN not overload” indication to eHRPD RRM.     -   5. eHRPDeAN stop broadcast “EUTRAN overloaded” indication in the         overhead message. If OtherRATNeighborList message is also         supported, eAN resume OtherRATNeighborList message normal         operation.     -   6. UE detect non-existence of “EUTRAN not overload” indication         from eAN. UE resume normal operation and re-select and switch to         LTE when switching requirements are met.

Example Embodiment 2

-   -   1. eNB sends RRCConnectionRelease message with redirection to         eHRPD and includes “EUTRAN overloaded” indication.     -   2. Upon receiving the eNB downlink message, UE switch to eHRPD         system. UE then sends ConnectionRequest message and include         “EUTRAN overloaded” indication to eAN. The UE that switched from         LTE to eHRPD system only include the “EUTRAN overloaded”         indication in the first ConnectionRequest message send to eAN.         As long as the UE remains in the eHRPD system, it does not         include the indication in the subsequent ConnectionRequest         messages.     -   3. Upon receiving first UE's uplink message (e.g.         ConnectionRequest message) with “EUTRAN overloaded” indication,         the eAN update the RRM and begin to send broadcast overhead         message with “EUTRAN overloaded” indication. eAN (or RRM)         initiate and starts LTE Overload timer.     -   4. UEs receives overhead message with “EUTRAN overloaded”         temporally disable the LTE system re-selection function and does         not attempt to switch to LTE system.     -   5. eAN has not detect any more UEs sends ConnectionRequest         message with “ETURAN overloaded” indication and LTE Overload         timer expires. eAN stop includes “EUTRAN overloaded” indication         in the overhead message.     -   6. UE detect non-existence of “EUTRAN not overload” indication         from eAN. UE resume normal operation and re-select and switch to         LTE when switching requirements are met.

Example Embodiment 3

-   -   1. eNB sends RRCConnectionRelease message with redirection to         eHRPD and includes “EUTRAN overloaded” indication.     -   2. Upon receiving the eNB downlink message, UE switch to eHRPD         system. UE then sends ConnectionRequest message and include         “EUTRAN overloaded” indication to eAN. The UE that switched from         LTE to eHRPD system only include the “EUTRAN overloaded”         indication in the first ConnectionRequest message send to eAN.         As long as the UE remains in the eHRPD system, it does not         include the indication in the subsequent ConnectionRequest         messages.     -   3. Upon receiving first UE's uplink message (e.g.         ConnectionRequest message) with “EUTRAN overloaded” indication,         the eAN update the RRM and begin to send broadcast overhead         message with “EUTRAN overloaded” indication. eAN (or RRM)         initiate and starts LTE Overload timer. eAN either stop         broadcast OtherRATNeighborList message or modify the parameters         in the OtherRATNeighborList message such that UE is not able to         switch to LTE as long as it can acquire HRPD channels.     -   4. UEs receives overhead message with “EUTRAN overloaded”         temporally disable the LTE system re-selection function and does         not attempt to switch to LTE system.     -   5. eAN has not detect any more UEs sends ConnectionRequest         message with “ETURAN overloaded” indication and LTE Overload         timer expires. eAN stop includes “EUTRAN overloaded” indication         in the overhead message. eAN also resume broadcasting         OtherRATNeighborList message and using normal parameters for         OtherRATNeighborList message.     -   6. UE detect non-existence of “EUTRAN not overload” indication         from eAN. UE resume normal operation and re-select and switch to         LTE when switching requirements are met.

The present invention provides mechanism to prevent UE switching back to the preferred (or primary/source) network from backup (or secondary/target) network when preferred (or primary/source) network is overloaded. The mechanism prevents UEs ping-ponging between two systems due to overload situation at the preferred network.

ABBREVIATIONS

eAN: Enhanced Access Network

HRPD: High Rate Packet Data

LTE: Long Term Evolution

UE: User Equipment

E-UTRAN: Evolved UMTS Terrestrial Radio Access

RAT: Radio access technology

RRM: Radio Resource Management

Although the invention has been described in detail in the foregoing embodiments for the purpose of illustration, it is to be understood that such detail is solely for that purpose and that variations can be made therein by those skilled in the art without departing from the spirit and scope of the invention except as it may be described by the following claims. 

The invention claimed is:
 1. A method of a node of a secondary Radio Access Technology (RAT) that is in communication with a primary node of a primary RAT and User Equipments (UEs) that are able to communicate by way of the primary and secondary RATs, the method comprising the steps of: receiving at a network interface unit of the node of the secondary RAT a message that indicates that the primary RAT is in an overload condition, wherein the receiving includes receiving from a UE of the UEs an uplink message that the primary RAT is in an overload condition; forming with a processing unit of the node UE messages for the UEs not to try to communicate with the primary RAT; and sending the messages through the network interface unit of the node to the UEs.
 2. The method of claim 1, wherein the sending step includes the step of sending a broadcast message to the UEs with an indication that the primary RAT is in the overload condition and each UE is not to switch back to the primary RAT.
 3. The method of claim 1, wherein the sending step includes the step of the broadcast message affecting an Other RAT Neighbor List Function in each UE so that each UE does not switch back to the primary RAT.
 4. The method of claim 1, including the step of stopping sending the indication that the primary RAT is in the overload condition in the broadcast message from the network interface unit of the node after the network interface unit has not received the uplink message for a predetermined time from any of the UEs that the primary RAT is overloaded.
 5. A node of a secondary Radio Access Technology (RAT) that is in communication with a primary node of a primary RAT and User Equipments (UEs) that are able to communicate by way of the primary and secondary RATs, the node comprising: a network interface unit of the node of the secondary RAT which receives a message that indicates that the primary RAT is in an overload condition, wherein the network interface unit receives from a UE of the UEs an uplink message that the primary RAT is in an overload condition; and a processing unit of the node which forms UE messages for the UEs not to try to communicate with the primary RAT, the network interface unit of the node sending the messages to the UEs.
 6. The node of claim 5, including a broadcast message is sent from the network interface unit to the UEs with an indication that the primary RAT is in the overload condition and each UE is not to switch back to the primary RAT.
 7. The node of claim 5, wherein the broadcast message effecting an Other RAT Neighbor List Function in each UE so that each UE does not switch back to the primary RAT.
 8. The node of claim 5, wherein the network interface unit stops sending the indication that the primary RAT is in the overload condition in the broadcast message from the network interface unit of the node after the network interface unit has not received the uplink message for a predetermined time from any of the UEs that the primary RAT is overloaded. 